MIMEType of folder
Hello, When requested for MIMEType/ContentType for a folder, what should be the result? -- Rajath S, M.Sc(Hons.) Physics, Birla Institute of Technology and Science - Pilani, Pilani
Re: MIMEType of folder
Hello, description of getContentType(): returns a type string, which is unique for that type of content (e.g. "application/vnd.sun.star.hierarchy-folder"). is a folder's unique content type application/vnd.sun.star.hierarchy-folder? On Sun, Jun 16, 2013 at 1:07 PM, Rajath Shashidhara < rajaths.raja...@gmail.com> wrote: > Hello, > > When requested for MIMEType/ContentType for a folder, what should be the > result? > > > -- > Rajath S, > M.Sc(Hons.) Physics, > Birla Institute of Technology and Science - Pilani, > Pilani > -- Rajath S, M.Sc(Hons.) Physics, Birla Institute of Technology and Science - Pilani, Pilani
Re: [RELEASE]:_ new snapshot build based on trunk rev 1491858
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Claudio Filho wrote: >> As I had to test some stuff, I added pt-BR to a new build, the PO file >> were downloaded from the pootle server last night (get an idea of the >> status of the translation by that time), they are located here: >> http://people.apache.org/~arielch/developer-snapshots/new/ > > My hero!!! \o/ Good. ;-) - -- Albino B Neto < bino...@binoanb.eti.br > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJRvZhwAAoJEKKu5IjHmpTP8acP+QE1er7OnoPS81yhyP5mFina fX2ViB5sDfuqQf7oEOiVJBI0eZMslt3jIKnE7BcCbg3gs/ghz13fIXJ0hdFOIler y4GdMyQw03L11aGaV+55bFqppjXFnP+yYqkJsQOo93QcKFit5j9iXsK+pXxjxCuf pY39zL3n83LXLAKeo4o9dM4Ptpolby687hKlIHK4EDDjN9NujkZ63XUKcadETNRy 9rDOC/edakDkXOH5n20W5o5VGuXScVEOKvR7esuK9WRQDccy+TDFFCZy1Fjl/TEV fGeOPk2DcQR42bKK9tvGvztzom+y9Qqw7m2PiHxbucFEncVSxbdNnUtgAJ9GB48u DPIWxDM1lDaRFd8mRRu8lqLj58p/Os9a37ay0emuE5fKu8Lm3YICSBLBIZcTLJli rDfeignoo4HdaGCkURTjg1yjYRaW5gRZaaG2s7NyN//sS0XKyt3dLPd1nNVgd5PA 0cPQiDn/FqyLh0dVHtlhTViguy5JOX7OMmBdjj+8k1I03F/PY10Th22iYanyYnm9 DgHwlJ5UEm+dbVKJaazJNgT1XrQ7Gaxlj3bho8UFRVP4dbwTvZyV8wXWiZXeAX1m U+LvxQtUX/+NsS3+dXD5EaGuEEbI7dlM0UsYgGJs9ssmoNuCzsGyA0ZpkS/fKyoM 9ZPR18wIMaQegpMzyNsA =SSTm -END PGP SIGNATURE- - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Idea: Public beta program for AOO 4.1?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rob Weir wrote: > Something to consider for AOO 4.1 is the value of a broad public beta > program to solicit early feedback on builds. This could be a good > complement to our formal QA efforts. +1 I was thinking about it, long time ago. - -- Albino B Neto < bino...@binoanb.eti.br > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJRvcfzAAoJEKKu5IjHmpTPWi4P/1TNwya52c7XeGajY9AClBgg gTlcAO+AqUMb642uy1jdc01e3bxELZumfVVFAONrbOIihR0yaVClzyUKlpFjOalf zbBIG4X1iuQGBdk4Z0jHTMQsqb7REosAvh94MAOPwKC5x1Rci1UYC6YAihNtIpFG w4i1zFKVnnjTFY52SzcaHjiuqY8le5mwI7rZWa0mn+7951scW5ZIXkBWUuY6ee46 lgphH7KBUlINMjEfQFH9nE9/cUUqfyHXVryoW9g7ZEaJ4gjZMq0GKc67QfrbZ4fl aTnpyoi5i5cz+lmWTgciYZpMBY3pIvU0ndbZwW/BqkrMuNNzPdSoPqYDsnEuiqUe sOzzt0Lr/4cxaV7vZylgXwXd+E3cOXC+1JVUJcAs11IIKDXUkvlMZO5sN38Prb/Q /jqPkSEHCTVJl/+YO7yGorv1qBxNZiY/tStJ8KTn306+OPi4iYlXDutfVtLAyDtQ BdZxVCBqJZKUBVHy6vvSwR17ejM735GnvmeKtAIn17hvFPIGAZ/wX/EDtxnOqSEE 85ksBf6VKorK/Vk5zOOIO3a7Jvb9zHL8I+y7ctiWTnmJtXkXfWM4r8byDi5+G3V9 ZKRbDTG4/jfEGZUnb9C7NrvDyxEAyPW0KXf0xyzeQ5RNalJzbKIfyL/AX/NlhwvO qU1ZffBVZbqPH0rdtyVg =zv+Z -END PGP SIGNATURE- - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: MIMEType of folder
If you are talking about content items within an ODF Package, whether a path is considered that of a folder is determined in the ODF Package manifest.xml file. The manifest.xml file will specify the MIME TYPE of the collection of items having the same path in the beginning of their file names when that collection has significance taken as a unit (more than just sharing a common prefix on their names). *** If you are not asking about that case, you can stop here *** TMI;DNR Some implementations create manifest.xml file entries for folders for no particular purpose (the MIME TYPE is not set). These are unnecessary. There is no requirement to have every path segment reflected in the manifest. Only those that prefix a collection of items where the collection has a specific MIME type need to be distinguished. The MIMETYPE indicates what is special about items in that particular collection other than their names having a common prefix of "/"-separated parts. "Folders" have MIMETYPE entries, for example, when the items of another ODF document are embedded in another ODF document instead of embedding the other document's package as a single item. The common prefix on the Zip file names of those embedded items will have an entry that provides the ODF MIMETYPE for the embedded document. Actual files embedded in the ODF package, including another ODF package as a single file are required to have entries in manifest.xml that gives their MIMETYPEs. You might need to experiment to see if the Apache OpenOffice SDK or source-code objects you are using return a default MIMETYPE for manifest entries having no specified MIMETYPE and whether it will do that even for paths used in the filenames and not identified in the manifest. I suspect that happens if the API you are using provides navigation of the package as if it is a hierarchical collection of folders. This is a synthesis. The files in the Zip have no hierarchical organization, although the contained files can have names of a hierarchical form, often for conceptual convenience and as a way to keep names separated into useful non-conflicting categories, such as "META-INF/...", "Configurations2/...", etc. Please note that this narrative is from the perspective of the ODF specifications, not incidentals of implementations, even though those incidentals matter if you encounter them in the API or object model of Apache OpenOffice. - Dennis -Original Message- From: Rajath Shashidhara [mailto:rajaths.raja...@gmail.com] Sent: Sunday, June 16, 2013 02:38 AM To: dev Subject: Re: MIMEType of folder Hello, description of getContentType(): returns a type string, which is unique for that type of content (e.g. "application/vnd.sun.star.hierarchy-folder"). is a folder's unique content type application/vnd.sun.star.hierarchy-folder? On Sun, Jun 16, 2013 at 1:07 PM, Rajath Shashidhara < rajaths.raja...@gmail.com> wrote: > Hello, > > When requested for MIMEType/ContentType for a folder, what should be the > result? > > > -- > Rajath S, > M.Sc(Hons.) Physics, > Birla Institute of Technology and Science - Pilani, > Pilani > -- Rajath S, M.Sc(Hons.) Physics, Birla Institute of Technology and Science - Pilani, Pilani - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: MIMEType of folder
Hi Rajath, On Sun, Jun 16, 2013 at 01:07:00PM +0530, Rajath Shashidhara wrote: > Hello, > > When requested for MIMEType/ContentType for a folder, what should be the > result? read the API doc carefully: http://www.openoffice.org/api/docs/common/ref/com/sun/star/ucb/Content.html Properties - Mandatory properties - ContentType "contains a unique type string for the content ( i.e. "application/vnd.sun.star.hierarchy-link" ). This property is always read-only. The ContentType should not be confused with the MIME media type ( MIME types ) of the content. Media types may be provided through the optional property "MediaType". The value of this property should match the information on creatable contents given by UCB contents that implement the property "CreatableContentsInfo"." a) do not confuse ContentType with MediaType (the MIME type) b) the value of ContentType is up to the implementation, search for application/ in main/ucb/source/ucp/ to get an idea http://opengrok.adfinis-sygroup.org/source/search?q=application%2F&path=%2Faoo-trunk%2Fmain%2Fucb%2Fsource%2Fucp%2F&project=aoo-trunk Something like application/cmis-content-folder application/cmis-content-document Regards -- Ariel Constenla-Haile La Plata, Argentina pgpOWO6rfL_ld.pgp Description: PGP signature
Re: MIMEType of folder
Hello, I created a new UNO project with some modified code and renamed it to CMISContentProvider and deleted my old project. I created the .oxt for new project and installed it in the extension manager. But, the error stack trace printed by my test client application still points to my previous CMISContentProvider. My stack trace shows error from connectToRepository() which is not there any more in my new project. How do I resolve this?
Re: MIMEType of folder
On Sun, Jun 16, 2013 at 11:10:56PM +0530, Rajath Shashidhara wrote: > Hello, > > I created a new UNO project with some modified code and renamed it to > CMISContentProvider and deleted my old project. I created the .oxt for new > project and installed it in the extension manager. But, the error stack > trace printed by my test client application still points to my previous > CMISContentProvider. My stack trace shows error from connectToRepository() > which is not there any more in my new project. > > How do I resolve this? I don't understand what you've done, but it looks like you have the two versions installed at the same time; the obvious: did you restart the application completely? If restarting does not work, remove the user profile with all the extensions. By the way, how are you debugging all this? You should debug both the client application and the UNO component, at the same time. Regards -- Ariel Constenla-Haile La Plata, Argentina pgpCDKV0SqFA1.pgp Description: PGP signature
Re: euskal encounter 2013
On 16/06/2013 RGB ES wrote: I did a quick translation into Spanish http://people.apache.org/~rgb-es/AOO_Flyer-ES.odt Thanks! I think it's best to shorten columns a bit to make sure they fit, if you have doubts about fonts. For the time being, I've listed the available translations at http://www.openoffice.org/marketing/marketing_where.html (a very, very outdated page, but still easily reachable from search engines), just to keep them tracked. Also, the original EN doc have a missing half paragraph under "Base", it seems, because there is a phrase that makes no sense. If you fix the translation according to Rory's explanation, pelase keep it at the same URL, to avoid breaking the link. As for your other comment in the ODT file: I think it's fine to localize trademark notices. Sooner or later, this stuff ought to be made available in Pootle too... Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: service ResultSet
On Fri, Jun 14, 2013 at 12:00:55AM +0530, Rajath Shashidhara wrote: > Hello Ariel, > > for making the ucp return the same single component factory object, shall I > create a static single component factory object and return it if it is not > null and create a new one if it is null? By this way we can return the same > single component factory object. Please study this example: http://people.apache.org/~arielch/extensions/OneInstanceJob.zip It has a UNO component implementing a css.task.Job. The Job will be instantiated every time a new document is created or loaded. With the standard factory helper, createInstanceWithContext returns always a new instance; with the modified factory helper in that example, there is only one instance of the job. > Although, one thing I have not understood is what is the consequences of > returning different single component factory objects? The difference is in having several instances of your content provider, versus having a single instance during all the application lifetime. Recall: you have to cache UCB contents, you may get several call to queryContent() with the same content id, one after the other, and you should return the same content. Side note: caching contents does not mean caching content's properties; on the contrary, your implementation should decide which properties are cachable and which not (see for example isCachable() in ucb/source/ucp/webdav/ContentProperties.cxx). Regards -- Ariel Constenla-Haile La Plata, Argentina pgpy2MPTGYtKx.pgp Description: PGP signature
Re: MIMEType of folder
Hello Ariel, I'm debugging with the help of Log Statements. Is there any other way? On Mon, Jun 17, 2013 at 12:09 AM, Ariel Constenla-Haile wrote: > On Sun, Jun 16, 2013 at 11:10:56PM +0530, Rajath Shashidhara wrote: > > Hello, > > > > I created a new UNO project with some modified code and renamed it to > > CMISContentProvider and deleted my old project. I created the .oxt for > new > > project and installed it in the extension manager. But, the error stack > > trace printed by my test client application still points to my previous > > CMISContentProvider. My stack trace shows error from > connectToRepository() > > which is not there any more in my new project. > > > > How do I resolve this? > > I don't understand what you've done, but it looks like you have the two > versions installed at the same time; the obvious: did you restart the > application completely? If restarting does not work, remove the user > profile with all the extensions. > > By the way, how are you debugging all this? You should debug both the > client application and the UNO component, at the same time. > > > Regards > -- > Ariel Constenla-Haile > La Plata, Argentina > -- Rajath S, M.Sc(Hons.) Physics, Birla Institute of Technology and Science - Pilani, Pilani
Re: MIMEType of folder
Hello Ariel, I'm debugging the client application using breakpoints and step-by-step execution. I'm using Log statements in the UNO component. Is there a way to use stpe-by-step executions for the UNO Component as well? On Mon, Jun 17, 2013 at 1:28 AM, Rajath Shashidhara < rajaths.raja...@gmail.com> wrote: > Hello Ariel, > > I'm debugging with the help of Log Statements. > Is there any other way? > > > On Mon, Jun 17, 2013 at 12:09 AM, Ariel Constenla-Haile < > arie...@apache.org> wrote: > >> On Sun, Jun 16, 2013 at 11:10:56PM +0530, Rajath Shashidhara wrote: >> > Hello, >> > >> > I created a new UNO project with some modified code and renamed it to >> > CMISContentProvider and deleted my old project. I created the .oxt for >> new >> > project and installed it in the extension manager. But, the error stack >> > trace printed by my test client application still points to my previous >> > CMISContentProvider. My stack trace shows error from >> connectToRepository() >> > which is not there any more in my new project. >> > >> > How do I resolve this? >> >> I don't understand what you've done, but it looks like you have the two >> versions installed at the same time; the obvious: did you restart the >> application completely? If restarting does not work, remove the user >> profile with all the extensions. >> >> By the way, how are you debugging all this? You should debug both the >> client application and the UNO component, at the same time. >> >> >> Regards >> -- >> Ariel Constenla-Haile >> La Plata, Argentina >> > > > > -- > Rajath S, > M.Sc(Hons.) Physics, > Birla Institute of Technology and Science - Pilani, > Pilani > -- Rajath S, M.Sc(Hons.) Physics, Birla Institute of Technology and Science - Pilani, Pilani
Re: MIMEType of folder
On Mon, Jun 17, 2013 at 01:28:03AM +0530, Rajath Shashidhara wrote: > Hello Ariel, > > I'm debugging with the help of Log Statements. > Is there any other way? The proper way is setting break points in the source, watching variables, etc. How are you deploying your extension? How are you debugging it? The task is: inside the same IDE, you have to debug your component once the extension is installed; and you have to test it with a client application that you also have to debug. Right-click on the project root inside NetBeans, the context menu has some AOO specific options: a) Debug Extension in target AOO b) Deploy and Run Extension in AOO (a) will create a user profile inside the build folder (build/soffice_debug) that will be removed every time you clean the project. The extension will be installed for this user profile only. This has some advantages and some drawbacks, one is that the client application to test the extension cannot use the simple bootstrap mechanism because it is likely to boostrap an office with your default user profile, not this profile inside the build directory of your NB project. One possible solution to debug both the extension and the client application: - configure the JVM used by AOO to listen for debugger connections, see http://wiki.openoffice.org/wiki/Scripting_in_Java_with_NetBeans_IDE#Java_configuration_in_OpenOffice.org_Options_dialog (do not use port 8000 as in the example, choose other number like 9009) - deploy the extension in your default user profile - attach the debugger: inside NetBeans, menu Debug - Attach Debugger (see http://wiki.openoffice.org/wiki/File:023_attach_debugger_config.png but change the port to the one you chose in the step above) - set break points in the extension/component sources - set break points in the client application - Debug the client application Ctr + F5 with the project select With this steps you should be able to debug the client application and the UNO component together, while the first uses the second. Draw back: every time you change your component's sources you should deploy the extension (and restart the office). Regards -- Ariel Constenla-Haile La Plata, Argentina pgp8qOSiCGO7E.pgp Description: PGP signature
Re: [DISCUSS] a new web area for Apache OpenOffice third party products
On Fri, Jun 14, 2013 at 4:11 PM, Kay Schenk wrote: > > > On Fri, Jun 14, 2013 at 10:31 AM, Rob Weir wrote: > >> On Fri, Jun 14, 2013 at 12:14 PM, Kay Schenk >> wrote: >> . >> . >> . >> >> >>> >>> > >> >>> >>> > Levels in which we might do things: >> >>> >>> > >> >>> >>> > Level 1 -- Do nothing but watch for abuses. If someone wants to >> >>> sell >> >>> >>> > a CD, then they are free to do it, per the license. They can >> >>> >>> > advertise on eBay, their website, etc., but they have no >> permission >> >>> to >> >>> >>> > use the trademarks. Nothing special on our website. >> >>> >>> > >> >>> >>> >> >>> >>> >> >>> >>> > >> >>> >>> > Level 2 -- We allow a listing on our website (or wiki) of those >> who >> >>> >>> > offer CDs. But we make no attempt to verify anything. It is >> all >> >>> >>> > "caveat emptor". We put in disclaimers on the page so users >> know >> >>> that >> >>> >>> > we have not vetted anything. >> >>> >>> > >> >>> >>> > Level 3 -- We review requests for listing and approve them only >> if >> >>> >>> > they meet our qualifications, which might include proper use of >> >>> >>> > trademarks, a link back to our website, etc. This is similar to >> what >> >>> >>> > we did with consultants. >> >>> >>> > >> >>> >>> > Level 4 -- Like Level 3, but for those distributors who meet our >> >>> >>> > qualifications we offer a special logo they can use, something >> like >> >>> a >> >>> >>> > "Community Distributor". >> >>> >>> > >> . >> . >> . >> >> >>> >> >> >> > It seems there is at least some consensus of moving ahead with a CD >> vendor >> > page similar to the consultants page: >> > >> > http://www.openoffice.org/bizdev/consultants.html >> > >> > so, Rob, if you feel inclined to work on #1 and #2 from your suggestions >> > above, please feel free to draft up something for us to review. Then >> move >> > on to #3? >> > >> >> We might be able to jump directly to #3. We don't need to do #1 or #2 >> first. >> >> I've started to draft the "Distributor Best Practices" page here: >> >> http://www.openoffice.org/distribution/best-practices.html >> > > ok, this looks pretty good... > > >> >> I think in the end we need three pages: >> >> 1) The main page, which is the listings page. >> >> 2) The Distributor Best Practices page >> >> 3) An instructions page for would-be distributors, of how to get >> listed. It might grow over time to include links to ISO's, CD labels, >> etc., in the future. >> >> These pages would be cross-linked. >> >> >> > So, we don't have to un-reroute what we've already done with the old >> > distribution area, I'm inclined to put this new CD page(s) in bizdev >> also. >> > >> > I'm hoping we can just implement this with xml and xslt. I'll do some >> > testing in a day or so. >> > >> >> That could be done now or later on. It is OK to start with a static >> HTML page (not MDText) and prototype the design and even go live with >> it, and then add the XSLT automation to generate it later. Depending >> on the number of listings automation might not be needed. >> >> Do you want to mock up a distributor listings page? >> > > Yes, I can do this over the next day or so I think. I just do up a static > HTML as you suggest. Maybe like the old listing but without the region info > -- to start. > > > I started looking at some XML, and XSL just now, and well, not sure how > this could be handled with the CMS vis a vis standard page headers etc. > We could probaly define a "new" page type. > > For now, static HTML it is. > OK, start here (revision of /distribution/index.html) http://www.openoffice.org/distribution/index_new.html Mockups needing MUCH discussion I'm sure. > >> >> Regards, >> >> -Rob >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> > > > -- > > - > MzK > > "Normal is not something to aspire to, it is something to get away from." > > -- Jodie Foster > > -- - MzK "Normal is not something to aspire to, it is something to get away from." -- Jodie Foster
Re: Article on the Register
On 14/06/2013 Rob Weir wrote: If we agree on this kind of division, then "news" or "announcements" would refer to project blog posts of a certain style. They are the more formal ones written with the intent of giving a specific message. For the time being I've just committed the "minimal" version, i.e., http://www.openoffice.org/ now has a block with the three latest blog posts. As for switching completely to the blog, I'm undecided. Having an article published at an openoffice.org URL instead than blogs.apache.org gives a more "official" connotation to it. Maybe we can just leave things as they are and rename "News" into "Announcements", i.e., articles with a more "official" tone that are meant to be featured on the homepage for longer periods (after all, this is how we are using "News" at the moment). Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS] a new web area for Apache OpenOffice third party products
On Sun, Jun 16, 2013 at 5:38 PM, Kay Schenk wrote: > On Fri, Jun 14, 2013 at 4:11 PM, Kay Schenk wrote: > >> >> >> On Fri, Jun 14, 2013 at 10:31 AM, Rob Weir wrote: >> >>> On Fri, Jun 14, 2013 at 12:14 PM, Kay Schenk >>> wrote: >>> . >>> . >>> . >>> >>> >>> >>> > >>> >>> >>> > Levels in which we might do things: >>> >>> >>> > >>> >>> >>> > Level 1 -- Do nothing but watch for abuses. If someone wants to >>> >>> sell >>> >>> >>> > a CD, then they are free to do it, per the license. They can >>> >>> >>> > advertise on eBay, their website, etc., but they have no >>> permission >>> >>> to >>> >>> >>> > use the trademarks. Nothing special on our website. >>> >>> >>> > >>> >>> >>> >>> >>> >>> >>> >>> >>> > >>> >>> >>> > Level 2 -- We allow a listing on our website (or wiki) of those >>> who >>> >>> >>> > offer CDs. But we make no attempt to verify anything. It is >>> all >>> >>> >>> > "caveat emptor". We put in disclaimers on the page so users >>> know >>> >>> that >>> >>> >>> > we have not vetted anything. >>> >>> >>> > >>> >>> >>> > Level 3 -- We review requests for listing and approve them only >>> if >>> >>> >>> > they meet our qualifications, which might include proper use of >>> >>> >>> > trademarks, a link back to our website, etc. This is similar to >>> what >>> >>> >>> > we did with consultants. >>> >>> >>> > >>> >>> >>> > Level 4 -- Like Level 3, but for those distributors who meet our >>> >>> >>> > qualifications we offer a special logo they can use, something >>> like >>> >>> a >>> >>> >>> > "Community Distributor". >>> >>> >>> > >>> . >>> . >>> . >>> >>> >>> >>> >> >>> > It seems there is at least some consensus of moving ahead with a CD >>> vendor >>> > page similar to the consultants page: >>> > >>> > http://www.openoffice.org/bizdev/consultants.html >>> > >>> > so, Rob, if you feel inclined to work on #1 and #2 from your suggestions >>> > above, please feel free to draft up something for us to review. Then >>> move >>> > on to #3? >>> > >>> >>> We might be able to jump directly to #3. We don't need to do #1 or #2 >>> first. >>> >>> I've started to draft the "Distributor Best Practices" page here: >>> >>> http://www.openoffice.org/distribution/best-practices.html >>> >> >> ok, this looks pretty good... >> >> >>> >>> I think in the end we need three pages: >>> >>> 1) The main page, which is the listings page. >>> >>> 2) The Distributor Best Practices page >>> >>> 3) An instructions page for would-be distributors, of how to get >>> listed. It might grow over time to include links to ISO's, CD labels, >>> etc., in the future. >>> >>> These pages would be cross-linked. >>> >>> >>> > So, we don't have to un-reroute what we've already done with the old >>> > distribution area, I'm inclined to put this new CD page(s) in bizdev >>> also. >>> > >>> > I'm hoping we can just implement this with xml and xslt. I'll do some >>> > testing in a day or so. >>> > >>> >>> That could be done now or later on. It is OK to start with a static >>> HTML page (not MDText) and prototype the design and even go live with >>> it, and then add the XSLT automation to generate it later. Depending >>> on the number of listings automation might not be needed. >>> >>> Do you want to mock up a distributor listings page? >>> >> >> Yes, I can do this over the next day or so I think. I just do up a static >> HTML as you suggest. Maybe like the old listing but without the region info >> -- to start. >> >> >> I started looking at some XML, and XSL just now, and well, not sure how >> this could be handled with the CMS vis a vis standard page headers etc. >> We could probaly define a "new" page type. >> >> For now, static HTML it is. >> > > OK, start here (revision of /distribution/index.html) > > http://www.openoffice.org/distribution/index_new.html > This is a good start. I wonder if the main page (index.html) should the end-user facing page, e.g., the distributor listings? And then have the FAQ be in distributor-faqs.html or something like that? Not a big deal, just an idea. Do we know what existing incoming links from 3rd party websites point to? (or even OO websites?) Whatever URL was used for the distributor list before should probably stay as the listing page. That way the existing links will still be accurate. http://www.openoffice.org/distribution/distributors.html Instead of "Location" maybe "Countries Served" or something like that. Or, in the application process we have a "data dictionary" that explains exactly what we want in each field. (I'm assuming that it would be common for someone in the US to be able to sent to Canada easily, and someone within the EU can cover more than one country if they want. "Additional Information"? I'd drop that unless we think it is really necessary. Otherwise it is easy for that to turn into an advertisement. Additional information can go on their website. > Mockups needing MUCH discussion I'm sure. > It is a good start. Maybe we iterate just a little bit mo
Draft blog post: With Apache OpenOffice you get what you don't pay for
https://blogs.apache.org/preview/OOo/?previewEntry=with_apache_openoffice_you_get -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Silent Installation on Installation Guide
On 6/7/13, Alexandro Colorado wrote: > On Wed, Jun 5, 2013 at 1:08 AM, O.Felka wrote: > >> Am 04.06.2013 22:49, schrieb Juergen Schmidt: >> >> Am Dienstag, 4. Juni 2013 um 21:17 schrieb Alexandro Colorado: >>> I would like to clarify the silent installation process in AOO, the Installation guide (which is for OOo) talks about running an MSI. At the moment Windows versions are in an .exe file, no MSI to be found. Q uestion i s, do we still have silent installation process and if so? How to perform such installation? The silent installation is a Microsoft Installer (MSI) feature and not >> an OOo/AOo special. >> If you call "Start -> Run -> 'msiexec /?'" you'll see all options of the >> MSI. >> > > I wonder if we have any of these reported on the wiki, when going through > the installation guide they report me that they get a dialog asking to use > the setup.exe after plugging the flags on the guide. > > Here is a screenshot: > http://imagebin.org/260566 > > Checking the guide I see there is a post on the forum that has an updated > version for 3.x ( > http://forum.openoffice.org/en/forum/viewtopic.php?f=74&t=28765&p=275147#p275147). > Althought the process is a bit convoluted, they need an extension ( > http://wiki.services.openoffice.org/wiki/Documentation%20%20/Administration_Guide/Deactivating_Registration_Wizard) > in order to get rid of a wizard. > > start /wait msiexec /qn /norestart /i openofficeorg3x.msi ADDLOCAL=All > REMOVE=gm_o_Onlineupdate > > Can anyone shed some light on this guide. > > Any ideas how to solve it? > >> >> Regards, >> Olaf >> >> >> >>> The exe us a self extracting zip file. When you look to the unpacked >>> files you will see the msi >>> >>> Juergen >>> Regards. -- Alexandro Colorado Apache OpenOffice Contributor http://es.openoffice.org >>> >>> >>> >> >> --**--**- >> To unsubscribe, e-mail: >> dev-unsubscribe@openoffice.**apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> > > > -- > Alexandro Colorado > Apache OpenOffice Contributor > http://es.openoffice.org > -- Alexandro Colorado Apache OpenOffice Contributor http://es.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Congratulations to Andrea and Andrew!
Congratulations too. Great news! On 6/11/2013 7:06 PM, Rob Weir wrote: Both Andrea Pescetti and Andrew Rist were among those elected as new ASF Members. Congratulations for the well-deserved recognition! -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
