Missing libraries

Francois Stephany wrote:
>I'm fed up with the titles like "Ruby and Rails successor", "MeteorJS
>killer". This is simply not true.

Yes - we should not try to to win prizes that were already given to others.
For sure it can be done more elegant in Pharo ... but no one will care.

>I don't care I have to use the 30 year old command line and text editor. It
>works; I can implement and deploy an API in a matter of minutes with Rails
>or Sinatra.

We should also not forget that Pharo is missing a good text editor as well.
Not only for Smalltalk code but also for other language or resources like
XML, JSON, ...

>0. Oh shit this image needs PharoV2.sources. Where the hell is it?

Did you notice the setting: System -> Download sources file
Maybe it is not obvious enough or turned off by default

Situation will improve as it is planned for Pharo 4 to integrate
Sources into the image if I understood correctly.

>1. Loading Seaside. Mmm. Where is the configuration? Oh, there are three
>different repos that looks all the same.

By default you should not care. Just load it.

Just go to world menu  
   Tools -> ConfigurationBrowser and load Seaside.

>3. How should I structure my packages ? I now have my own best practices
>that I've built by looking at other people code and by trial-and-errors.

I think this is a problem of Seaside not coming with some example apps to
look at. The sushi store is long gone and I dont know why it is not part
of Seaside anymore to verify that changes do not break existing apps.

This is really a problem as people usually look at examples, clone/change them
first. Reading tutorials and books often comes as a second step (if ever).

>4. How do I commit my external files? I have loads of js, css and images.
>Monticello will take forever every time I commit.

If you want a "Pharo only" solution use a subclass of WAFileMetadataLibrary,
and yes: Monticello is not the best tool to manage that.  

For real world scenarios (with Apache/Nginx frontend, ...) you will serve
resources externally anyway:
   http://de.slideshare.net/esug/real-world-seaside-applications

I agree that out of the box for "Seaside" newbies it is not easy to know about/
get used to WAFileLibrary, WAFileMetadataLibrary or uploading via
http://localhost/config/files
compared to the usual "create resource subfolder" in file centric environments.

Thanks
Torsten


       

 




     
     


_______________________________________________
Pharo-business mailing list
[hidden email]
http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org

> I think this is a problem of Seaside not coming with some example apps to
> look at. The sushi store is long gone and I dont know why it is not part
> of Seaside anymore to verify that changes do not break existing apps.

i am really wondering the same. Why the Sushi example was removed.

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Pharo-business mailing list
[hidden email]
http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org

On 13 Mar 2014, at 13:31, Alexandre Bergel <[hidden email]> wrote:

>> I think this is a problem of Seaside not coming with some example apps to
>> look at. The sushi store is long gone and I dont know why it is not part
>> of Seaside anymore to verify that changes do not break existing apps.
>
> i am really wondering the same. Why the Sushi example was removed.

I actually never saw that example. Has it ever been ported to Seaside 3 ?

Johan

_______________________________________________
Pharo-business mailing list
[hidden email]
http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org

No idea, but the sushi example was the basic example on how to run a simple but not trivial application.

Alexandre


On Mar 13, 2014, at 9:52 AM, Johan Brichau <[hidden email]> wrote:

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Pharo-business mailing list
[hidden email]
http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org

Hey Alex,

I subscribe to the idea, but I don't think we should focus on the Sushi example.
I think the following links provide much better examples:
- http://book.seaside.st/
- http://www.swa.hpi.uni-potsdam.de/seaside/tutorial 

Agreed, the seaside.st website needs an update. I definitely want to help there (I've been doing small things recently).
For me, it's on my stack but I'm focusing on other Seaside-related works first now (updates, gemstone, automated tests).

Johan

On 13 Mar 2014, at 13:54, Alexandre Bergel <[hidden email]> wrote:


_______________________________________________
Pharo-business mailing list
[hidden email]
http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org

Yeah, but missed the persistence part, a really important one if you want to develop a real app.
Of course, with gemstone is enough, but not all customer are agnostic about the persistence technology and they usually force you to use some specific relational database.
On the other hand, rails integrates everything from ui to database...

Sent from a device I don't want to advertise

_______________________________________________
Pharo-business mailing list
[hidden email]
http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org

>
> We should also not forget that Pharo is missing a good text editor as well.

We are working on it. This is the cross that igor is currently carrying.



_______________________________________________
Pharo-business mailing list
[hidden email]
http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org

_______________________________________________
Pharo-business mailing list
[hidden email]
http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org