Menu
▾
▴
exist-development — eXist Developer's List
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(22) |
Nov
(85) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(47) |
Feb
(127) |
Mar
(268) |
Apr
(78) |
May
(47) |
Jun
(38) |
Jul
(131) |
Aug
(221) |
Sep
(187) |
Oct
(54) |
Nov
(111) |
Dec
(84) |
| 2011 |
Jan
(152) |
Feb
(106) |
Mar
(94) |
Apr
(90) |
May
(53) |
Jun
(20) |
Jul
(24) |
Aug
(37) |
Sep
(32) |
Oct
(70) |
Nov
(22) |
Dec
(15) |
| 2012 |
Jan
(33) |
Feb
(110) |
Mar
(24) |
Apr
(1) |
May
(11) |
Jun
(8) |
Jul
(12) |
Aug
(37) |
Sep
(39) |
Oct
(81) |
Nov
(38) |
Dec
(50) |
| 2013 |
Jan
(23) |
Feb
(53) |
Mar
(23) |
Apr
(5) |
May
(19) |
Jun
(16) |
Jul
(16) |
Aug
(9) |
Sep
(21) |
Oct
(1) |
Nov
(2) |
Dec
(8) |
| 2014 |
Jan
(16) |
Feb
(6) |
Mar
(27) |
Apr
(1) |
May
(10) |
Jun
(1) |
Jul
(4) |
Aug
(10) |
Sep
(19) |
Oct
(22) |
Nov
(4) |
Dec
(6) |
| 2015 |
Jan
(3) |
Feb
(6) |
Mar
(9) |
Apr
|
May
(11) |
Jun
(23) |
Jul
(14) |
Aug
(10) |
Sep
(10) |
Oct
(9) |
Nov
(18) |
Dec
(4) |
| 2016 |
Jan
(5) |
Feb
(5) |
Mar
|
Apr
(2) |
May
(15) |
Jun
(2) |
Jul
(8) |
Aug
(2) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
(12) |
Mar
(22) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(5) |
Oct
(2) |
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(7) |
Oct
(19) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dmitriy S. <sha...@gm...> - 2012-05-15 05:51:36
|
+1 On Tue, May 15, 2012 at 2:19 AM, Adam Retter <ad...@ex...> wrote: > I propose that after 2.0 release - > > 1) I upgrade our SourceForge project to the latest software platform > version on SourceForge. This gives us some shiny new features and > options but will change the URL or our source repos. > > 2) We migrate from Subversion to Git (still on SourceForge), there is > a tool for doing this - > git://github.com/jcoglan/svn2git.git > > 3) I shift the project layout of trunk to follow a standard project > layout and update the Ant build to work with this. > This will make our planned move to Maven much easier and allow me to > carry on that work. > -- Dmitriy Shabanov |
|
From: Adam R. <ad...@ex...> - 2012-05-14 21:20:05
|
I propose that after 2.0 release - 1) I upgrade our SourceForge project to the latest software platform version on SourceForge. This gives us some shiny new features and options but will change the URL or our source repos. 2) We migrate from Subversion to Git (still on SourceForge), there is a tool for doing this - git://github.com/jcoglan/svn2git.git 3) I shift the project layout of trunk to follow a standard project layout and update the Ant build to work with this. This will make our planned move to Maven much easier and allow me to carry on that work. -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Casey J. <cas...@jo...> - 2012-04-01 18:23:00
|
What would be the benefit over what we are using now? 2012/3/31 Вячеслав Седов <sch...@gm...> > http://www.7-zip.org/sdk.html "Java source code for LZMA compression > and decompression" > > 31 марта 2012 г. 17:06 пользователь Вячеслав Седов > <sch...@gm...> написал: > > 31 марта 2012 г. 16:42 пользователь Evgeny Gazdovsky > > <gaz...@gm...> написал: > >> There is no java tools for 7-zip, only C, C++ java bindig. > >> > >> 29 марта 2012 г. 13:47 пользователь Вячеслав Седов < > sch...@gm...> > >> написал: > >>> > >>> hello, > >>> > >>> what about supporting 7-zip archives in eXist-db? > >>> > >>> nice idea - ye? > >>> > >>> with best wishes, > >>> Slav > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> This SF email is sponsosred by: > >>> Try Windows Azure free for 90 days Click Here > >>> http://p.sf.net/sfu/sfd2d-msazure > >>> _______________________________________________ > >>> Exist-development mailing list > >>> Exi...@li... > >>> https://lists.sourceforge.net/lists/listinfo/exist-development > >> > >> > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- -- Casey Jordan easyDITA a product of Jorsek LLC "CaseyDJordan" on LinkedIn, Twitter & Facebook (585) 348 7399 easydita.com This message is intended only for the use of the Addressee(s) and may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, please be advised that any disclosure copying, distribution, or use of the information contained herein is prohibited. If you have received this communication in error, please destroy all copies of the message, whether in electronic or hard copy format, as well as attachments, and immediately contact the sender by replying to this e-mail or by phone. Thank you. |
|
From: Вячеслав С. <sch...@gm...> - 2012-03-31 13:07:12
|
http://www.7-zip.org/sdk.html "Java source code for LZMA compression and decompression" 31 марта 2012 г. 17:06 пользователь Вячеслав Седов <sch...@gm...> написал: > 31 марта 2012 г. 16:42 пользователь Evgeny Gazdovsky > <gaz...@gm...> написал: >> There is no java tools for 7-zip, only C, C++ java bindig. >> >> 29 марта 2012 г. 13:47 пользователь Вячеслав Седов <sch...@gm...> >> написал: >>> >>> hello, >>> >>> what about supporting 7-zip archives in eXist-db? >>> >>> nice idea - ye? >>> >>> with best wishes, >>> Slav >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF email is sponsosred by: >>> Try Windows Azure free for 90 days Click Here >>> http://p.sf.net/sfu/sfd2d-msazure >>> _______________________________________________ >>> Exist-development mailing list >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-development >> >> |
|
From: Вячеслав С. <sch...@gm...> - 2012-03-31 13:06:10
|
31 марта 2012 г. 16:42 пользователь Evgeny Gazdovsky <gaz...@gm...> написал: > There is no java tools for 7-zip, only C, C++ java bindig. > > 29 марта 2012 г. 13:47 пользователь Вячеслав Седов <sch...@gm...> > написал: >> >> hello, >> >> what about supporting 7-zip archives in eXist-db? >> >> nice idea - ye? >> >> with best wishes, >> Slav >> >> >> ------------------------------------------------------------------------------ >> This SF email is sponsosred by: >> Try Windows Azure free for 90 days Click Here >> http://p.sf.net/sfu/sfd2d-msazure >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development > > |
|
From: Dannes W. <di...@ex...> - 2012-03-30 08:11:40
|
Hi On 26 mrt. 2012, at 14:36, Ian Wright <ian...@we...> wrote: > Any news on when we can expect the final 1.4.2 version? I planned to release last week, but I was too busy :) I think it will be ultimato half of april. Only a few thinghies need to be wrapped up, but the code base is ready (i can't recall any issues that should be resolved) Cheers Dannes |
|
From: Dannes W. <di...@ex...> - 2012-03-30 08:10:49
|
On 26 mrt. 2012, at 14:36, Ian Wright <ian...@we...> wrote: > Any news on when we can expect the final 1.4.2 version? I see some recent messages on some issues. Cheers Dannes |
|
From: Вячеслав С. <sch...@gm...> - 2012-03-29 09:47:28
|
hello, what about supporting 7-zip archives in eXist-db? nice idea - ye? with best wishes, Slav |
|
From: Вячеслав С. <sch...@gm...> - 2012-03-28 12:54:35
|
thank you for fast fixing, Wolfgang by the way - maybe better case for rewriter is to produce code similar to //user[@id eq '1'][parent::users[not(parent::*)]]? also i've heard about statistics-based optimization in eXist - how far it from finish state? i know that for xml-databases it is almost endless road (in compare to SQL), but i mean at least first iteration with best wishes, Slav 28 марта 2012 г. 12:42 пользователь Wolfgang Meier <wol...@ex...> написал: >> for xpath like /users/user[@id eq '1'] it rewrite code to >> //users/user[@id eq '1'] > > Slav, thanks for the test. I just fixed this in rev 16202: > > http://exist.svn.sourceforge.net/exist/?rev=16202&view=rev > > Wolfgang |
|
From: Wolfgang M. <wol...@ex...> - 2012-03-28 08:42:24
|
> for xpath like /users/user[@id eq '1'] it rewrite code to > //users/user[@id eq '1'] Slav, thanks for the test. I just fixed this in rev 16202: http://exist.svn.sourceforge.net/exist/?rev=16202&view=rev Wolfgang |
|
From: Вячеслав С. <sch...@gm...> - 2012-03-27 09:43:56
|
for xpath like /users/user[@id eq '1'] it rewrite code to
//users/user[@id eq '1']
test case
groups.xml
<?xml version="1.0" encoding="UTF-8"?>
<groups>
<group>
<users>
<user id="1"/>
</users>
</group>
<group>
<users>
<user id="1"/>
</users>
</group>
</groups>
users.xml
<?xml version="1.0" encoding="UTF-8"?>
<users>
<user id="1"/>
<user id="2"/>
</users>
xpath /users/user[@id eq '1'] (with rewriter turned on) return
<user id="1"/>
<user id="1"/>
<user id="1"/>
when rewriter turned off work as expected
with best wishes,
Slav
|
|
From: Joe W. <jo...@gm...> - 2012-03-26 17:40:45
|
Hi Wolfgang, > this was my fault: I had to change some classes in the XQuery api to > implement partially applied functions. Obviously I missed to build the > content extraction module. I committed a fix. Great, thank you! I just updated and was able to rebuild with contentextraction=true. Joe |
|
From: Wolfgang M. <wol...@ex...> - 2012-03-26 15:48:06
|
Hi Joe, this was my fault: I had to change some classes in the XQuery api to implement partially applied functions. Obviously I missed to build the content extraction module. I committed a fix. Wolfgang |
|
From: Ian W. <ian...@we...> - 2012-03-26 14:53:09
|
Hi, Any news on when we can expect the final 1.4.2 version? Thanks, Ian |
|
From: Joe W. <jo...@gm...> - 2012-03-26 14:24:10
|
Looking at my console, I realize that the messages that appeared
immediately above what I sent in my last message might be helpful as well -
so here it is:
extension-contentextraction:
prepare:
[mkdir] Created dir:
/Users/joe/Documents/workspace/exist-trunk/extensions/contentextraction/classes
[fetch] Class org.apache.ivy.Main is already present, skipping download.
[ivy:retrieve] :: loading settings :: url =
jar:file:/Users/joe/Documents/workspace/exist-trunk/tools/ant/lib/ivy-2.2.0.jar!/org/apache/ivy/core/settings/ivysettings.xml
[ivy:retrieve] :: resolving dependencies ::
org.exist#tika;working@choskimac-ii.local
[ivy:retrieve] confs: [default]
[ivy:retrieve] found org.apache.tika#tika-parsers;0.9 in public
[ivy:retrieve] found org.apache.tika#tika-core;0.9 in public
[ivy:retrieve] found edu.ucar#netcdf;4.2-min in public
[ivy:retrieve] found org.apache.james#apache-mime4j;0.6 in public
[ivy:retrieve] found org.apache.pdfbox#pdfbox;1.4.0 in public
[ivy:retrieve] found org.apache.pdfbox#fontbox;1.4.0 in public
[ivy:retrieve] found org.apache.pdfbox#jempbox;1.4.0 in public
[ivy:retrieve] found org.bouncycastle#bcmail-jdk15;1.45 in public
[ivy:retrieve] found org.bouncycastle#bcprov-jdk15;1.45 in public
[ivy:retrieve] found org.apache.poi#poi;3.7 in public
[ivy:retrieve] found org.apache.poi#poi-scratchpad;3.7 in public
[ivy:retrieve] found org.apache.poi#poi-ooxml;3.7 in public
[ivy:retrieve] found org.apache.poi#poi-ooxml-schemas;3.7 in public
[ivy:retrieve] found org.apache.xmlbeans#xmlbeans;2.3.0 in public
[ivy:retrieve] found dom4j#dom4j;1.6.1 in public
[ivy:retrieve] found
org.apache.geronimo.specs#geronimo-stax-api_1.0_spec;1.0.1 in public
[ivy:retrieve] found org.ccil.cowan.tagsoup#tagsoup;1.2 in public
[ivy:retrieve] found asm#asm;3.1 in public
[ivy:retrieve] found com.drewnoakes#metadata-extractor;2.4.0-beta-1 in
public
[ivy:retrieve] found de.l3s.boilerpipe#boilerpipe;1.1.0 in public
[ivy:retrieve] found rome#rome;0.9 in public
[ivy:retrieve] :: resolution report :: resolve 297ms :: artifacts dl 15ms
[ivy:retrieve] :: evicted modules:
[ivy:retrieve] org.apache.geronimo.specs#geronimo-stax-api_1.0_spec;1.0 by
[org.apache.geronimo.specs#geronimo-stax-api_1.0_spec;1.0.1] in [default]
---------------------------------------------------------------------
| | modules || artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
---------------------------------------------------------------------
| default | 22 | 0 | 0 | 1 || 21 | 0 |
---------------------------------------------------------------------
[ivy:retrieve] :: retrieving :: org.exist#tika
[ivy:retrieve] confs: [default]
[ivy:retrieve] 21 artifacts copied, 0 already retrieved (20912kB/560ms)
|
|
From: Joe W. <jo...@gm...> - 2012-03-26 14:19:49
|
Hi all,
I've just tried building trunk (2.1dev rev. 16194) with the content
extraction feature enabled in local.build.properties. I get this error:
compile:
[echo] ----------------------------------
[echo] Compiling Content Extraction extensions
[echo] ----------------------------------
[echo] Compiling with Java 1.6 from 1.6 source to 1.6 target, debug
on, optimize on, deprecation off
[javac] Compiling 6 source files to
/Users/joe/Documents/workspace/exist-trunk/extensions/contentextraction/classes
[javac]
/Users/joe/Documents/workspace/exist-trunk/extensions/contentextraction/src/org/exist/contentextraction/xquery/ContentFunctions.java:259:
cannot find symbol
[javac] symbol : method getFunctionCall()
[javac] location: class org.exist.xquery.value.FunctionReference
[javac] FunctionCall call = ref.getFunctionCall();
[javac] ^
[javac] Note:
/Users/joe/Documents/workspace/exist-trunk/extensions/contentextraction/src/org/exist/contentextraction/xquery/ContentFunctions.java
uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 1 error
BUILD FAILED
/Users/joe/Documents/workspace/exist-trunk/build/scripts/build-impl.xml:777:
The following error occurred while executing this line:
/Users/joe/Documents/workspace/exist-trunk/extensions/contentextraction/build.xml:77:
Compile failed; see the compiler error output for details.
I'm not sure what the cause or solution is, but I'm happy to try any
suggestions.
Thanks,
Joe
|
|
From: Jens Ø. P. <oe...@gm...> - 2012-03-24 17:57:14
|
On Mar 24, 2012, at 4:22 PM, Dannes Wessels wrote: > On Saturday, March 24, 2012 at 12:02 , Dmitriy Shabanov wrote: >> Why should spend time on porting? Trunk don't have major changers (and should not have any till final release). So, much simpler mark next point from trunk. > sounds like the way to go :-) I will leave that decision to you pro's. But let's not forget this! A leaner eXist will also be easier to document. Jens > > D. > |
|
From: Dannes W. <da...@ex...> - 2012-03-24 15:22:34
|
On Saturday, March 24, 2012 at 12:02 , Dmitriy Shabanov wrote: > Why should spend time on porting? Trunk don't have major changers (and should not have any till final release). So, much simpler mark next point from trunk. sounds like the way to go :-) D. |
|
From: Dmitriy S. <sha...@gm...> - 2012-03-24 11:02:14
|
On Sat, Mar 24, 2012 at 3:45 PM, Jens Østergaard Petersen <oe...@gm... > wrote: > build/cruisecontrol > it can be remove because not in use. > roadmap > This should be updated or removed (better update IMHO) > webapp/administration > authentication example moved to it own folder, deleting this one... Why should spend time on porting? Trunk don't have major changers (and should not have any till final release). So, much simpler mark next point from trunk. -- Dmitriy Shabanov |
|
From: Jens Ø. P. <oe...@gm...> - 2012-03-24 10:45:38
|
Hi, I wonder if it would not be a good idea to do some basic housekeeping before releasing 2.0? Some things appear to me to have been moved from trunk five weeks ago that might better have been deleted or moved to the attic. Browsing through trunk, there is a lot of stuff that has not been touched for several years - some of it for as long as five years! This might mean that it is a gem of coding that never needs revision, but it may also mean that it is cruft, and there is no reason why people poking around in the code should stop and wonder what the meaning of such things is. I am sure that there are things I do not understand the function of, and that is my fault, but I list here a few things that struck me as being in need of examination: backrest bin/ batch.d deprecated build/cruisecontrol roadmap webapp/administration developper.html I notice that deprecated, build/cruisecontrol, and developper.html were not ported to 2.0, but they should perhaps be removed from trunk as well? Is there a list of what was not ported? In stable, there is no way of telling how old things are. What made me look into this was webapp/administration - it sounded awfully important, and was even partly functional, but it was hard for me to see what to use it for. I think there is also the question how long to keep the Sandbox open, when eXide gives so much more (but no sample queries, I know). First time users will wonder why they are given two apps that (sort of) do the same thing. Cheers, Jens |
|
From: Jens Ø. P. <oe...@gm...> - 2012-03-21 18:07:17
|
Hi Wolfgang, Thanks for your anwers. I got into this because I often fiddle around off-line - and Tamboti had started using a CDN, so this had become impossible. I will add code to page.html in Tamboti to make it easy to switch between CDN (for serving) and local files (for developing). I will try to upgrade jquery to 1.7.1 in admin and eXide. Tamboti works with 1.7.1., so I will upload jquery-1.7.1.min.js and jquery-ui.min.js to webapp/scripts/jquery/ tomorrow. jquery 1.6.2 is referenced in apps: doc, demo, fundocs, TEIXLingual (page.html) webapp: jquery.xql, admin.xql, login.xql, eXide, urlrewrite.xml jquery 1.5 is referenced in apps: TEIXLingual (browse.xql); here it is loaded from the app and I will not change this - I think you know why! jquery 1.4.4 is referenced in webapp: repo/packages/mobile-function-doc/index.xql. I won't touch jquery-mobile stuff. jquery 1.4.2 is referenced in apps: TEIXLingual (test.html), I take it this is not a used page and I will not change this. webapp: WEB-INF/classes/META-INF/resources/scripts/(dojo/)syntaxhighlighter_3.0.83/tests/. This is read in from betterFORM. jquery 1.4.1 is mentioned (not referenced) in webapp/administration/scripts/jquery/descriptor.xml jquery 1.2.6 is mentioned in webapp/WEB-INF/classes/META-INF/resources/scripts/simile/timeline/timeline_ajax/. This is read in from betterFORM. The docs app (index.html and james-hambley-page-design-template.html) is a little strange, since it only loads jquery for IE. I guess jquery is not really needed, but will not touch. As you know, jquery-1.6.2.min.js is stored in webapp/scripts/jquery/. betterFORM reads in jquery-1.4.2.js in webapp/WEB-INF/classes/META-INF/resources/scripts/dojo/syntaxhighlighter_3.0.83/tests/js/ and in webapp/WEB-INF/classes/META-INF/resources/scripts/syntaxhighlighter_3.0.83/tests/js/ jquery-1.4.1.min.js, jquery-1.4.1.js and jquery-1.3.2.js (all three!) are stored in webapp/administration/scripts/jquery/ - and they are not referenced anywhere, as far as I can see. I have no idea what http://localhost:8080/exist/administration/index.xql is supposed to do. There are more than 3 MB worth of files in this folder and it is two years since anyone committed anything. Can't code like this - which sounds awfully important, but which isn't - be moved to the attic? Best, Jens On Mar 21, 2012, at 3:49 PM, Wolfgang Meier wrote: > Hi Jens, > >> Is there a policy about how we link to js libraries (jQuery libraries)? > > I frequently work without network connection, so I prefer to have a > local copy of libraries, though the better practice is to use a CDN. > The core jquery libraries are mirrored in webapp/scripts/jquery/ > because they are required by tools which are essential parts of eXist > (eXide, admin interface). > > Other libraries should be provided by the corresponding apps though. > >> Should they be stored locally or downloaded from a CDN (making off-line development impossible)? If a CDN is to be used, is there a preference, say, for ajax.googleapis.com? Should one link to "1.7" in order to get 1.7.2 when it comes out - or is that risky? > > Updating a javascript library is sometimes a bit tricky because the > browser may not reload all scripts at the same time, thus leading to > hickups. I would thus rather link to a specific version. > >> If they are stored locally, is the preference to store them in the app using it or in webapp? > > In the app, unless it's jquery or jquery.ui. > >> Is there a policy that only minified libraries should be stored locally? jquery-utils.js in webapp is small and it would make little difference, but should the minified version be used? > > If possible, use a minified version. > >> The libraries I wish to use are jquery-1.7.1.min.js and jquery-ui.min.js. > > Well, I think you have two options: update the jquery version in eXist > and make sure eXide, tamboti and the admin web app continue to work. > Add your own jquery-1.7.1.min.js to your application. > > Wolfgang |
|
From: Wolfgang M. <wol...@ex...> - 2012-03-21 14:49:27
|
Hi Jens, > Is there a policy about how we link to js libraries (jQuery libraries)? I frequently work without network connection, so I prefer to have a local copy of libraries, though the better practice is to use a CDN. The core jquery libraries are mirrored in webapp/scripts/jquery/ because they are required by tools which are essential parts of eXist (eXide, admin interface). Other libraries should be provided by the corresponding apps though. > Should they be stored locally or downloaded from a CDN (making off-line development impossible)? If a CDN is to be used, is there a preference, say, for ajax.googleapis.com? Should one link to "1.7" in order to get 1.7.2 when it comes out - or is that risky? Updating a javascript library is sometimes a bit tricky because the browser may not reload all scripts at the same time, thus leading to hickups. I would thus rather link to a specific version. > If they are stored locally, is the preference to store them in the app using it or in webapp? In the app, unless it's jquery or jquery.ui. > Is there a policy that only minified libraries should be stored locally? jquery-utils.js in webapp is small and it would make little difference, but should the minified version be used? If possible, use a minified version. > The libraries I wish to use are jquery-1.7.1.min.js and jquery-ui.min.js. Well, I think you have two options: update the jquery version in eXist and make sure eXide, tamboti and the admin web app continue to work. Add your own jquery-1.7.1.min.js to your application. Wolfgang |
|
From: Jens Ø. P. <oe...@gm...> - 2012-03-21 11:15:12
|
Hi, Is there a policy about how we link to js libraries (jQuery libraries)? Should they be stored locally or downloaded from a CDN (making off-line development impossible)? If a CDN is to be used, is there a preference, say, for ajax.googleapis.com? Should one link to "1.7" in order to get 1.7.2 when it comes out - or is that risky? If they are stored locally, is the preference to store them in the app using it or in webapp? Is there a policy that only minified libraries should be stored locally? jquery-utils.js in webapp is small and it would make little difference, but should the minified version be used? The libraries I wish to use are jquery-1.7.1.min.js and jquery-ui.min.js. Best, Jens |
|
From: Dannes W. <di...@ex...> - 2012-03-04 16:26:58
|
The changes have been synced..... -- Dannes Wessels On 29 feb. 2012, at 02:46, Joe Wicentowski <jo...@gm...> wrote: >> All tests now pass! >> >> Joe: Go ahead and merge into stable if you want... > > Nice work, Andrzej! I hit a problem with my 'svn merge' routine - > which I emailed this list about. As soon as I get that cleared up > I'll merge your changes and the updated documentation into stable. > > Joe |
|
From: Joe W. <jo...@gm...> - 2012-03-03 05:11:37
|
Hi all, In an attempt to move the current documentation out of the webapp directory and into a new .xar app, I just committed a new app to the eXist SVN repository in the exist/apps area. (There were more commits than I intended - sorry.) I'm aware of the longstanding project to migrate the documentation to DocBook 5 and revamp the organization, etc. This app is not intended to replace/displace that effort. This is just an attempt to bridge the gap for the purposes of the eXist 2.0 launch. If you want to try out the new app, check out exist/apps/doc, and run "ant" in the checked out directory to build the .xar file (it'll show up in build/doc-0.1.xar). Then install the xar file with admin > package repository. Then the app will be in: http://localhost:8080/exist/apps/doc Some known issues/to dos: - Only webapp/*.xml files were copied into the new app - This omits any documentation in subfolders of webapp, since they contain feature demos which belong in the "demo" app (some "demos" have already been moved, others needs to be moved) - The pure documentation from the subfolders should be edited to strip out the demo bits, instead linking to the demo content once it has been moved into the "demo" app - I haven't updated "documentation.xml" to reflect these omitted files - The documentation XSLT (stylesheets/db2html.xsl) and CSS (resources/css/exist.css) need work - Search form & functionality will be added in consultation with Wolfgang Feel free to report other problems here. Joe |
64 messages has been excluded from this view by a project administrator.
