Re: Package name
Am 24.02.2018 um 14:31 schrieb Matthias Seidel: Am 20.02.2018 um 22:50 schrieb Marcus: Am 20.02.2018 um 21:50 schrieb Matthias Seidel: Am 20.02.2018 um 19:43 schrieb Marcus: Am 20.02.2018 um 17:30 schrieb Matthias Seidel: To be more precise, it is only the description that seems wrong, not the package name itself. Changing "Mailcap module" to "Fonts module" should do the job... if it's just the description and it doesn't influence the code in some way, then IMHO just go ahead and change the text to a more descriptive one. I just wondered if there is a (for me) hidden logic behind the chosen description. ;-) then I think a little debugging is necessary *) and ... I didn't mean programming logic here... ;-) that doesn't matter. When you do changes you need to know where they get visible. When you don't know this, then you need to debug it - or test it in a different way. Anyway, I committed the changes now and forced a build from Linux64 buildbot. When it is done I will install it on Ubuntu. It is just a description and I don't expect more than optical differences. Marcus My local Windows build is just running, but the change may only be visible in DEB and RPM... build and test. I'm sure Mechtilde would help with the DEB packages and others with the RPM files. ;-) *) except there are devs that remember the purpose of the description and could speak-up here. Marcus Am 13.02.2018 um 22:21 schrieb Matthias Seidel: Hi all, when I look at: https://svn.apache.org/repos/asf/openoffice/trunk/main/setup_native/source/packinfo/packinfo_office.txt the package names look reasonable to me. All except one (copied from the installed DEB package): openoffice-ooofonts - Mailcap module for Apache OpenOffice 4.1.5 Why is a package containing fonts called mailcap module? Regards, Matthias - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Package name
Am 20.02.2018 um 22:50 schrieb Marcus: > Am 20.02.2018 um 21:50 schrieb Matthias Seidel: >> Am 20.02.2018 um 19:43 schrieb Marcus: >>> Am 20.02.2018 um 17:30 schrieb Matthias Seidel: To be more precise, it is only the description that seems wrong, not the package name itself. Changing "Mailcap module" to "Fonts module" should do the job... >>> >>> if it's just the description and it doesn't influence the code in some >>> way, then IMHO just go ahead and change the text to a more descriptive >>> one. >> >> I just wondered if there is a (for me) hidden logic behind the chosen >> description. ;-) > > then I think a little debugging is necessary *) and ... I didn't mean programming logic here... ;-) Anyway, I committed the changes now and forced a build from Linux64 buildbot. When it is done I will install it on Ubuntu. It is just a description and I don't expect more than optical differences. Regards, Matthias > >> My local Windows build is just running, but the change may only be >> visible in DEB and RPM... > > build and test. > > I'm sure Mechtilde would help with the DEB packages and others with > the RPM files. ;-) > > *) except there are devs that remember the purpose of the description > and could speak-up here. > > Marcus > > > Am 13.02.2018 um 22:21 schrieb Matthias Seidel: > > Hi all, > > when I look at: > > https://svn.apache.org/repos/asf/openoffice/trunk/main/setup_native/source/packinfo/packinfo_office.txt > > > > the package names look reasonable to me. > > All except one (copied from the installed DEB package): > > openoffice-ooofonts - Mailcap module for Apache OpenOffice 4.1.5 > > Why is a package containing fonts called mailcap module? > > Regards, Matthias > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > smime.p7s Description: S/MIME Cryptographic Signature
Re: Package name
Am 20.02.2018 um 21:50 schrieb Matthias Seidel: Am 20.02.2018 um 19:43 schrieb Marcus: Am 20.02.2018 um 17:30 schrieb Matthias Seidel: To be more precise, it is only the description that seems wrong, not the package name itself. Changing "Mailcap module" to "Fonts module" should do the job... if it's just the description and it doesn't influence the code in some way, then IMHO just go ahead and change the text to a more descriptive one. I just wondered if there is a (for me) hidden logic behind the chosen description. ;-) then I think a little debugging is necessary *) and ... My local Windows build is just running, but the change may only be visible in DEB and RPM... build and test. I'm sure Mechtilde would help with the DEB packages and others with the RPM files. ;-) *) except there are devs that remember the purpose of the description and could speak-up here. Marcus Am 13.02.2018 um 22:21 schrieb Matthias Seidel: Hi all, when I look at: https://svn.apache.org/repos/asf/openoffice/trunk/main/setup_native/source/packinfo/packinfo_office.txt the package names look reasonable to me. All except one (copied from the installed DEB package): openoffice-ooofonts - Mailcap module for Apache OpenOffice 4.1.5 Why is a package containing fonts called mailcap module? Regards, Matthias - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Package name
Am 20.02.2018 um 19:43 schrieb Marcus: > Am 20.02.2018 um 17:30 schrieb Matthias Seidel: >> >> To be more precise, it is only the description that seems wrong, not >> the package name itself. >> >> Changing "Mailcap module" to "Fonts module" should do the job... > > if it's just the description and it doesn't influence the code in some > way, then IMHO just go ahead and change the text to a more descriptive > one. I just wondered if there is a (for me) hidden logic behind the chosen description. ;-) My local Windows build is just running, but the change may only be visible in DEB and RPM... Regards, Matthias > > Marcus > > > >> Am 13.02.2018 um 22:21 schrieb Matthias Seidel: >>> >>> Hi all, >>> >>> when I look at: >>> >>> https://svn.apache.org/repos/asf/openoffice/trunk/main/setup_native/source/packinfo/packinfo_office.txt >>> >>> >>> the package names look reasonable to me. >>> >>> All except one (copied from the installed DEB package): >>> >>> openoffice-ooofonts - Mailcap module for Apache OpenOffice 4.1.5 >>> >>> Why is a package containing fonts called mailcap module? >>> >>> Regards, Matthias > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > smime.p7s Description: S/MIME Cryptographic Signature
Re: Package name
Am 20.02.2018 um 17:30 schrieb Matthias Seidel: To be more precise, it is only the description that seems wrong, not the package name itself. Changing "Mailcap module" to "Fonts module" should do the job... if it's just the description and it doesn't influence the code in some way, then IMHO just go ahead and change the text to a more descriptive one. Marcus Am 13.02.2018 um 22:21 schrieb Matthias Seidel: Hi all, when I look at: https://svn.apache.org/repos/asf/openoffice/trunk/main/setup_native/source/packinfo/packinfo_office.txt the package names look reasonable to me. All except one (copied from the installed DEB package): openoffice-ooofonts - Mailcap module for Apache OpenOffice 4.1.5 Why is a package containing fonts called mailcap module? Regards, Matthias - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Package name
No ideas? To be more precise, it is only the description that seems wrong, not the package name itself. Changing "Mailcap module" to "Fonts module" should do the job... Regards, Matthias Am 13.02.2018 um 22:21 schrieb Matthias Seidel: > > Hi all, > > when I look at: > > https://svn.apache.org/repos/asf/openoffice/trunk/main/setup_native/source/packinfo/packinfo_office.txt > > the package names look reasonable to me. > > All except one (copied from the installed DEB package): > > openoffice-ooofonts - Mailcap module for Apache OpenOffice 4.1.5 > > Why is a package containing fonts called mailcap module? > > Regards, Matthias > smime.p7s Description: S/MIME Cryptographic Signature
Re: Package name for new UNO components?
On Wed, Mar 22, 2017 at 8:14 PM, Matthias Seidel wrote: > Am 20.03.2017 um 20:01 schrieb Marcus: > > Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic: > >> Our pre-existing UNO components use service names of the form > >> com.sun.star.*, for example: > >> com.sun.star.comp.sdbc.calc.ODriver > >> com.sun.star.comp.io.TextInputStream > >> com.sun.star.comp.Calc.SpreadsheetDocument > >> > >> I am busy developing a new UNO component, a database driver for > >> PostgreSQL. > >> Should I rather use a prefix such as org.apache.openoffice.* for it > >> instead? > > > > Is it OK to mixup the namespaces within a specific module / code area? > > When you are sure that there won't be any side effects then it's maybe > > OK. > > > > However, to support the consistency within the OpenOffice code I would > > favour the old way. > > That would also be easier to integrate in the SDK... ;-) > > My component's service names would be the pre-existing services: com.sun.star.sdbc.Driver com.sun.star.sdbcx.Driver The interfaces also already exist: com.sun.star.lang.XServiceInfo com.sun.star.sdbc.XDriver com.sun.star.sdbcx.XDataDefinitionSupplier com.sun.star.sdbcx.XCreateCatalog com.sun.star.sdbcx.XDropCatalog Only the implementation name would be in the org.apache.openoffice.* module: org.apache.openoffice.sdbc.comp.postgresql.PostgresqlDriver This won't be visible in the SDK, and will mostly be used internally by DriverManager when connecting to the database.
Re: Package name for new UNO components?
Am 20.03.2017 um 20:01 schrieb Marcus: > Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic: >> Our pre-existing UNO components use service names of the form >> com.sun.star.*, for example: >> com.sun.star.comp.sdbc.calc.ODriver >> com.sun.star.comp.io.TextInputStream >> com.sun.star.comp.Calc.SpreadsheetDocument >> >> I am busy developing a new UNO component, a database driver for >> PostgreSQL. >> Should I rather use a prefix such as org.apache.openoffice.* for it >> instead? > > Is it OK to mixup the namespaces within a specific module / code area? > When you are sure that there won't be any side effects then it's maybe > OK. > > However, to support the consistency within the OpenOffice code I would > favour the old way. That would also be easier to integrate in the SDK... ;-) Matthias > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > smime.p7s Description: S/MIME Cryptographic Signature
Re: Package name for new UNO components?
Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic: Our pre-existing UNO components use service names of the form com.sun.star.*, for example: com.sun.star.comp.sdbc.calc.ODriver com.sun.star.comp.io.TextInputStream com.sun.star.comp.Calc.SpreadsheetDocument I am busy developing a new UNO component, a database driver for PostgreSQL. Should I rather use a prefix such as org.apache.openoffice.* for it instead? Is it OK to mixup the namespaces within a specific module / code area? When you are sure that there won't be any side effects then it's maybe OK. However, to support the consistency within the OpenOffice code I would favour the old way. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Package name for new UNO components?
One being? On Mon, Mar 20, 2017 at 7:41 PM, Mechtilde wrote: > Hello, > > do you know the existing one? > > Regards > > Mechtilde > > > Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic: > > Hi > > > > Our pre-existing UNO components use service names of the form > > com.sun.star.*, for example: > > com.sun.star.comp.sdbc.calc.ODriver > > com.sun.star.comp.io.TextInputStream > > com.sun.star.comp.Calc.SpreadsheetDocument > > > > I am busy developing a new UNO component, a database driver for > PostgreSQL. > > Should I rather use a prefix such as org.apache.openoffice.* for it > instead? > > > > Damjan > > > > >
Re: Package name for new UNO components?
Hi Damjan, If this an official part of AOO then why not org.apache.openoffice.uno.*? Regards, Dave > On Mar 20, 2017, at 10:41 AM, Mechtilde wrote: > > Hello, > > do you know the existing one? > > Regards > > Mechtilde > > > Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic: >> Hi >> >> Our pre-existing UNO components use service names of the form >> com.sun.star.*, for example: >> com.sun.star.comp.sdbc.calc.ODriver >> com.sun.star.comp.io.TextInputStream >> com.sun.star.comp.Calc.SpreadsheetDocument >> >> I am busy developing a new UNO component, a database driver for PostgreSQL. >> Should I rather use a prefix such as org.apache.openoffice.* for it instead? >> >> Damjan >> > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Package name for new UNO components?
Hello, do you know the existing one? Regards Mechtilde Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic: > Hi > > Our pre-existing UNO components use service names of the form > com.sun.star.*, for example: > com.sun.star.comp.sdbc.calc.ODriver > com.sun.star.comp.io.TextInputStream > com.sun.star.comp.Calc.SpreadsheetDocument > > I am busy developing a new UNO component, a database driver for PostgreSQL. > Should I rather use a prefix such as org.apache.openoffice.* for it instead? > > Damjan > signature.asc Description: OpenPGP digital signature
