You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have our core/... packages that are truly core to unipdf as it can be imported anywhere, should not rely on any other package (except internal utility packages).
It defines all the primitive types:
Would be interesting to get some input on this. We are always looking on ways to improve the internals, although it can take time and would obviously not appear until in a future major version.
The text was updated successfully, but these errors were encountered:
Currently we have our
core/...
packages that are truly core to unipdf as it can be imported anywhere, should not rely on any other package (except internal utility packages).It defines all the primitive types:
Would it be nicer to have
? or is that not specific enough, maybe
etc. ?
Similarly for
model
package, there are some pretty lengthy names:Clearly the name space in PDF models is pretty huge, however it might be possible to improve here. What about
or
Would be interesting to get some input on this. We are always looking on ways to improve the internals, although it can take time and would obviously not appear until in a future major version.
The text was updated successfully, but these errors were encountered: