[Seaside-dev] New contributions

[Avi Shefi]

Most of these sound interesting.
Other topics I have ran into that should be considered for inclusion into
Seaside:
+ Deployment tools for application paths and static files (a tree-view like
display which shows the structure of your application, as in any web
application suite, e.x. Eclipse).
+ Extensible prototyping of Javascript functionality in Seaside. The current
implementation of jQuery and Scriptaculous achieves this, but not in the
general sense. We should be able to express dependencies between components
on the client-side, there things happen using Javascript.
+ Comet scalability - using Seaside to serve Comet sessions between
different Smalltalk images.

Up until now I find myself digging into Seaside source code, trying to
figure out how things work.. I think this is an obstacle for newcomers to
Seaside development.

Hope things get clearer soon...


On Fri, Sep 3, 2010 at 1:53 AM, Julian Fitzell <jfitzell at gmail.com> wrote:

> Hi Avi,
>
> I'm sorry. I have your email starred for reply but just hadn't got to it. I
> really haven't had time to think carefully about it (which I wanted to do
> before replying), but off the top of my head:
>
> + there are a number of session-related nice-to-have features listed in the
> issue tracker. They're probably all tagged "security" I think - shout if you
> can't find them
> + the REST package Philippe started could do with some further
> experimentation and development
> + if you have any incentive to work on the new user experience, there is
> undoubtedly room for improvement to the new Welcome package
> + there's a distinct lack of admin/management/deployment
> infrastructure/tools - there's lots of room for new stuff here
> + the halos, admin toolbar, and so on have always been meant to be
> extensible but nobody ever seems to do so - I'm curious what other things
> might be useful there if someone put their mind to it
> + we'd also love people to work on the design and content of the website,
> the design of any of the built-in tools, or even useful attractive re-usable
> components, but those may not be up your alley...
>
> Do any of those seem interesting at all?
>
> We've unfortunately all been pretty busy over the past little while (which
> is why you're having trouble getting much response). You'll still find
> you'll get a response to specific questions; it's just hard to find much
> hand-holding. That said, we're determined to encourage more people to
> participate so with a little nagging, we'll try to provide as much guidance
> as we can.
>
> Julian
>
>
>
> On Wed, Sep 1, 2010 at 2:34 PM, Avi Shefi <avishefi at gmail.com> wrote:
>
>> bump :)
>>
>> On Sun, Aug 29, 2010 at 4:43 PM, Avi Shefi <avishefi at gmail.com> wrote:
>>
>>> Julian,
>>> I'm interested in getting to know Seaside on it's core, and
>>> exploring/adding new functionality missing in Seaside (which mostly requires
>>> an understanding of how Seaside works).
>>> Some areas that pop in my mind: custom URLs management, session
>>> management & caching, persistence, GUI (Javascript, jQuery, etc.) - to name
>>> a few.
>>>
>>> Any direction & guidance would be much appreciated.
>>>
>>>
>>>
>>>
>>> Thanks,
>>>
>>>  [image: Heartland]
>>> www.salepoint.co.il, www.redpoint.co.il
>>>  *Avi Shefi*
>>> Co-Founder & CTO
>>> *Mobile*: +972 54 5331705, *Email*: avishefi at gmail.com
>>>  On Sat, Aug 28, 2010 at 4:35 PM, Julian Fitzell <jfitzell at gmail.com>wrote:
>>>
>>>> Avi,
>>>>
>>>> Is there a particular area you're interested in? The BiteSize tasks are
>>>> probably a bit out of date so there may be other appropriate stuff - I'll
>>>> see if I can update those at ESUG, but we can point you in the right
>>>> direction for now.
>>>>
>>>> Julian
>>>>
>>>> On Fri, Aug 27, 2010 at 7:52 PM, Avi Shefi <avishefi at gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>> I'm new to Seaside development, and would like to start contributing.
>>>>> I have read the online Seaside book, which shows how to use Seaside,
>>>>> but doesn't depict how to start developing it.
>>>>>
>>>>> After reviewing the "BiteSize" tasks in the issue tracker I'm still
>>>>> wondering which easy task to begin with should I tackle first.
>>>>> Any suggestions? (please note that I will need some guidance, if
>>>>> possible)
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> seaside-dev mailing list
>>>>> seaside-dev at lists.squeakfoundation.org
>>>>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> seaside-dev mailing list
>>>> seaside-dev at lists.squeakfoundation.org
>>>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> seaside-dev mailing list
>> seaside-dev at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>>
>
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20100911/f90b114e/attachment.htm