including javascript and static files in a project.
Locked
including javascript and static files in a project.
 
|
i have been away from seaside for awhile. too much day job programming to do any fun programming.. just wondered how people were including javascript and other static files in their projects.
i really liked using monticello, but i never really got a handle on how to include all of the static files in the project so that other team members could use them and edit them (and check in their changes) without thinking about it at all..
does anyone have a clean and clever workflow? thanks! ----
peace, sergio photographer, journalist, visionary #BitMessage BM-2D8VWUJSS41RFKh1ec83preVabHrnniExa
http://www.ThoseOptimizeGuys.com http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101 _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Hi sergio,
The default answer is, use a web server between your seaside image and the actual webpage, and have this web server serve the including static files, since this is much faster than pulling them through your image … and more flexible, that other people can easily check them in. Cheers, Diego On Sep 19, 2013, at 8:37 PM, sergio_101 wrote:
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by sergio_101
Sergio, You are asking about the workflow during development, not just how to deploy, right? I guess this is where filetree and cypress will be the tools that rock. Instead of pressing all non-st artefacts into a file library and using monticello/store/envy to keep them under version control, turning things around and using today's standard vcs sytems for both non-st and st code will be the bright new world. But cypress is, to my knowledge, just an idea and some prototypes... For now, you can either do one of A) keep all in st and use WaFileLibrary. This locks out all non-st users in the team B) use separate repositories for st and non-st artefacts. This makes the whole process more complex, but non-st members have access C) create a sophisticated mix of A) and B). This is complicated and error-prone. Most of the work is needed to synchronize yor file library with the outer-world contents... C) is how most projects I am aware of do it. Most have troubles with that approach. Joachim Diego Lont <[hidden email]> schrieb: Hi sergio, The default answer is, use a web server between your seaside image and the actual webpage, and have this web server serve the including static files, since this is much faster than pulling them through your image … and more flexible, that other people can easily check them in. Cheers, Diego On Sep 19, 2013, at 8:37 PM, sergio_101 wrote:
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: including javascript and static files in a project.
|
|
thanks! this is about where everything was a while back. i don't like using WaFileLibrary, because then you get stuck editing a string in st. i would much rather let a designer use whatever tools they want to edit there files. the same with javascript files..
C just seems really hard to manage.. especially on a team of three or four specialized roles.. On Fri, Sep 20, 2013 at 3:36 AM, Joachim Tuchel <[hidden email]> wrote:
----
peace, sergio photographer, journalist, visionary #BitMessage BM-2D8VWUJSS41RFKh1ec83preVabHrnniExa http://www.ThoseOptimizeGuys.com http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101 _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Sergio, You can always upload/compile files into a file library. Iirc, there even is a web front end to upload files into a file library. So with a little good will and education, this can work for "external" files. But it's always just a workaround. Joachim
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by sergio_101
A little addition; We use rewrite rules on the deployment machine to redirect requests to the /files folder to a local directory. So one step in the deployment process is to export all our file libraries to that folder, the upside of this is that calls to #urlOf: can remain unchanged and apache handles all the external files. Still the fact that we need to import all files into a file library is less than optimal. But we use this in order to use self-contained images on development machines - no http server needed.., Joachim
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
«
Return to Seaside General
|
1 view|%1 views
| Free forum by Nabble | Edit this page |